-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Properly sort modules when building the API documentation #231
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nfelt14
added
bug
Something isn't working
documentation
Improvements or additions to documentation
labels
Jun 6, 2024
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #231 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 150 150
Lines 4138 4138
Branches 651 651
=========================================
Hits 4138 4138 ☔ View full report in Codecov by Sentry. |
…ght number of spaces
nfelt14
changed the title
docs: Always use alphabetical sorting for modules when building the API documentation
WIP: docs: Always use alphabetical sorting for modules when building the API documentation
Jun 6, 2024
…moved" This reverts commit a5d1270.
nfelt14
changed the title
WIP: docs: Always use alphabetical sorting for modules when building the API documentation
WIP: docs: Properly sort modules when building the API documentation
Jun 6, 2024
nfelt14
changed the title
WIP: docs: Properly sort modules when building the API documentation
docs: Properly sort modules when building the API documentation
Jun 6, 2024
michaelwagoner
approved these changes
Jun 6, 2024
Test Results (ubuntu)
|
Test Results (windows)
|
Test Results (macos)
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
The API documentation currently has the modules sorted non-alphabetically when built on a Unix OS, this PR fixes that.
Types of changes
What types of changes does your code introduce?
Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.